.planning/ROADMAP.md (1)

1-130: No additional issues in this file beyond the scope concern already noted.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.planning/ROADMAP.md around lines 1 - 130, Remove the stray
"[duplicate_comment]" marker from the review comment content associated with
"Roadmap: Release Process Migration" so the comment reads only the intended
sentence ("No additional issues in this file beyond the scope concern already
noted.")—locate the review text containing the duplicate token and delete it,
leaving the comment clean and unambiguous.

stream-chat-android-compose/src/main/res/drawable/stream_compose_ic_search.xml (1)

24-29: strokeColor should use a placeholder color, not a semantic gray.

The project convention for stream_compose_ic_*.xml drawables is to use a hardcoded placeholder color (e.g. #FFFFFF) because tint is applied programmatically by the Compose UI layer at runtime. Using #687385 (a specific semantic gray) embeds a design-specific value in the asset instead of a neutral placeholder. While Android's src_in tint mode will still override it at render time, it violates the established pattern and can cause the icon to render with the wrong color if the composable consumer forgets to apply a tint.

🎨 Proposed fix

-        android:strokeColor="#687385"
+        android:strokeColor="#FFFFFF"

Based on learnings: "For drawable XMLs named stream_compose_ic_*.xml in the stream-chat-android-compose module, use hardcoded placeholder colors because tint is applied programmatically when used in composables to ensure theme-aware coloring at runtime."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/res/drawable/stream_compose_ic_search.xml`
around lines 24 - 29, Replace the hardcoded semantic gray in the search drawable
with the project's placeholder color: open stream_compose_ic_search.xml and
change the android:strokeColor attribute (and any other explicit semantic colors
in this drawable) from "#687385" to the neutral placeholder (e.g. "#FFFFFF") so
the Compose layer can apply tint programmatically; ensure android:fillColor
remains transparent and strokeWidth/strokeLineCap/strokeLineJoin are unchanged.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/util/MessagePreviewIconFactory.kt (1)

67-132: Avoid undocumented suppression by extracting a small icon builder helper.

Line [67] introduces @Suppress("LongMethod") without rationale. Prefer removing the suppression and extracting duplication into a helper so the method stays within limits naturally.

♻️ Proposed refactor

-    `@Suppress`("LongMethod")
     override fun createPreviewIcons(): Map<String, InlineTextContent> {
         val placeholder = Placeholder(
             width = 14.sp,
             height = 14.sp,
             placeholderVerticalAlign = PlaceholderVerticalAlign.Center,
         )
         val iconModifier = Modifier.size(14.dp)
         return mapOf(
-            VOICE_MESSAGE to InlineTextContent(placeholder) {
-                Icon(
-                    modifier = iconModifier,
-                    painter = painterResource(id = R.drawable.stream_compose_ic_mic),
-                    contentDescription = null,
-                    tint = ChatTheme.colors.textSecondary,
-                )
-            },
-            PHOTO to InlineTextContent(placeholder) {
-                Icon(
-                    modifier = iconModifier,
-                    painter = painterResource(id = R.drawable.stream_compose_ic_camera),
-                    contentDescription = null,
-                    tint = ChatTheme.colors.textSecondary,
-                )
-            },
+            previewIcon(VOICE_MESSAGE, R.drawable.stream_compose_ic_mic, placeholder, iconModifier),
+            previewIcon(PHOTO, R.drawable.stream_compose_ic_camera, placeholder, iconModifier),
             // ...same for the rest
         )
     }
+
+    private fun previewIcon(
+        key: String,
+        drawableRes: Int,
+        placeholder: Placeholder,
+        iconModifier: Modifier,
+    ): Pair<String, InlineTextContent> =
+        key to InlineTextContent(placeholder) {
+            Icon(
+                modifier = iconModifier,
+                painter = painterResource(id = drawableRes),
+                contentDescription = null,
+                tint = ChatTheme.colors.textSecondary,
+            )
+        }

As per coding guidelines: "**/*.kt: Use @OptIn annotations explicitly; avoid suppressions unless documented".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/util/MessagePreviewIconFactory.kt`
around lines 67 - 132, Remove the undocumented `@Suppress`("LongMethod") on
MessagePreviewIconFactory.createPreviewIcons and refactor duplicated
InlineTextContent + Icon creation into a small private helper (e.g.,
buildPreviewIcon(drawableRes: Int): InlineTextContent) that captures the
Placeholder and Icon modifier; then replace each anonymous InlineTextContent
block (for VOICE_MESSAGE, PHOTO, VIDEO, FILE, LINK, LOCATION, POLL) with calls
to that helper, keeping Placeholder and iconModifier shared and eliminating the
long-method suppression.

.planning/STATE.md (1)

5-9: Consider adding an owner/update cadence for status freshness.

Lines 5–9 are time-sensitive and can become stale quickly; adding an “owner” and expected refresh cadence would reduce drift.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.planning/STATE.md around lines 5 - 9, Update the time-sensitive block by
adding explicit ownership and a refresh cadence so status remains fresh: add
fields such as "Owner: <team/person>" and "Refresh cadence: <frequency, e.g.
weekly/monthly/after-change>" alongside the existing "Phase", "Plan", "Status",
and "Last activity" entries, and include a short sentence describing who is
responsible for updates and when to update (e.g., "Owner will review and refresh
this status every X days or after significant changes").

.planning/PROJECT.md (1)

44-49: Add explicit target branch and coordination note in constraints.

Please include that changes should target develop and note release-owner coordination when touching changelog/release-process artifacts.

Based on learnings: Target develop branch for PRs; sync with release owners before touching versioning, publishing, or changelog scripts.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.planning/PROJECT.md around lines 44 - 49, Update the Constraints section to
explicitly state that PRs must target the develop branch and add a coordination
note that any changes to versioning, publishing, changelog or release-process
artifacts (e.g., CHANGELOG.md, release scripts) require prior sync with the
release owner; reference the "Constraints" heading and the file name
CHANGELOG.md so reviewers can find and enforce the rule.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/MessageReadStatusIcon.kt (1)

83-110: isErrorIcon slot is absent from the public overload, breaking customisation parity.

All four other delivery states (isReadIcon, isPendingIcon, isSentIcon, isDeliveredIcon) are exposed as slot parameters so integrators can override them. The newly-handled FAILED_PERMANENTLY branch (line 108) hard-wires IsErrorIcon with no override path. This is inconsistent with the rest of the API surface and prevents theming/branding of the error state.

♻️ Proposed refactor

 `@Composable`
 public fun MessageReadStatusIcon(
     message: Message,
     isMessageRead: Boolean,
     modifier: Modifier = Modifier,
     isMessageDelivered: Boolean = false,
     readCount: Int = 0,
     isReadIcon: `@Composable` () -> Unit = { IsReadCount(modifier = modifier, readCount = readCount) },
     isPendingIcon: `@Composable` () -> Unit = { IsPendingIcon(modifier = modifier) },
     isSentIcon: `@Composable` () -> Unit = { IsSentIcon(modifier = modifier) },
     isDeliveredIcon: `@Composable` () -> Unit = { IsDeliveredIcon(modifier = modifier) },
+    isErrorIcon: `@Composable` () -> Unit = { IsErrorIcon(modifier = modifier) },
 ) {
     val syncStatus = message.syncStatus

     when (syncStatus) {
         SyncStatus.IN_PROGRESS,
         SyncStatus.SYNC_NEEDED,
         SyncStatus.AWAITING_ATTACHMENTS,
         -> isPendingIcon()

         SyncStatus.COMPLETED -> when {
             isMessageRead -> isReadIcon()
             isMessageDelivered -> isDeliveredIcon()
             else -> isSentIcon()
         }

-        SyncStatus.FAILED_PERMANENTLY -> IsErrorIcon(modifier = modifier)
+        SyncStatus.FAILED_PERMANENTLY -> isErrorIcon()
     }
 }

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/MessageReadStatusIcon.kt`
around lines 83 - 110, The MessageReadStatusIcon API hard-codes IsErrorIcon for
SyncStatus.FAILED_PERMANENTLY and should expose an error slot for parity; add a
new parameter isErrorIcon: `@Composable` () -> Unit to MessageReadStatusIcon
(defaulting to { IsErrorIcon(modifier = modifier) }) and call that isErrorIcon()
in the FAILED_PERMANENTLY branch instead of directly invoking IsErrorIcon, so
integrators can override the error state rendering.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/UnreadCountIndicator.kt (1)

36-47: KDoc is missing the color parameter.

The public function signature exposes color as an overridable parameter whose default has just changed (from accentError to accentPrimary). Documenting its intent and the new default helps API consumers understand the change.

📝 Proposed addition

  * `@param` unreadCount The number of messages the user didn't read.
  * `@param` modifier Modifier for styling.
+ * `@param` color Background color of the badge. Defaults to [ChatTheme.colors.accentPrimary].
  */

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/UnreadCountIndicator.kt`
around lines 36 - 47, Update the KDoc for the composable function
UnreadCountIndicator to include the missing `@param` entry for color, describing
that it controls the badge tint and noting the default value
(ChatTheme.colors.accentPrimary) and its intent (to match the app's accent for
unread badges); keep other parameter docs intact and ensure the KDoc reflects
the changed default from the previous accentError to accentPrimary so callers
understand the behavioral change.

stream-chat-android-compose/src/main/res/values/strings.xml (1)

31-34: Prefer positional numeric placeholders in new plurals.

Using %1$d instead of %d makes translator-side reordering safer and keeps formatting style more localization-friendly.

♻️ Proposed i18n formatting tweak

     <plurals name="stream_compose_channel_list_typing_many">
-        <item quantity="one">%d person is typing</item>
-        <item quantity="other">%d people are typing</item>
+        <item quantity="one">%1$d person is typing</item>
+        <item quantity="other">%1$d people are typing</item>
     </plurals>
@@
     <plurals name="stream_compose_photos_preview">
-        <item quantity="one">%d Photo</item>
-        <item quantity="other">%d Photos</item>
+        <item quantity="one">%1$d Photo</item>
+        <item quantity="other">%1$d Photos</item>
     </plurals>
     <plurals name="stream_compose_videos_preview">
-        <item quantity="one">%d Video</item>
-        <item quantity="other">%d Videos</item>
+        <item quantity="one">%1$d Video</item>
+        <item quantity="other">%1$d Videos</item>
     </plurals>
     <plurals name="stream_compose_files_preview">
-        <item quantity="one">%d File</item>
-        <item quantity="other">%d Files</item>
+        <item quantity="one">%1$d File</item>
+        <item quantity="other">%1$d Files</item>
     </plurals>

Also applies to: 182-193

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@stream-chat-android-compose/src/main/res/values/strings.xml` around lines 31
- 34, The plural resource stream_compose_channel_list_typing_many uses
unpositioned numeric placeholders ("%d"); update both <item> entries to use
positional placeholders ("%1$d") so translators can reorder safely and maintain
consistent formatting; search for other plural resources (e.g., the similar
block referenced at lines 182-193) and apply the same replacement to their
numeric placeholders as well to ensure all plural strings use "%1$d".

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SearchResultItem.kt (2)

93-93: Verify that spacedBy plus inner padding matches the intended Figma gap.

Arrangement.spacedBy(spacingMd) (16dp) applies between all three children. Combined with the center content's own start = spacing2xs (4dp), the effective visual gap between the avatar and text is 20dp, not 16dp. If the design intent is exactly 16dp edge-to-edge, consider removing the center content's horizontal start padding, or removing the arrangement spacing and relying solely on per-child padding.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SearchResultItem.kt`
at line 93, The horizontalArrangement uses
Arrangement.spacedBy(StreamTokens.spacingMd) which adds 16dp between all
children while the center content also has start = StreamTokens.spacing2xs
(4dp), producing a 20dp gap; to match the Figma 16dp edge-to-edge spacing remove
the center content's start padding (the padding on the composable that sets
start = StreamTokens.spacing2xs) or alternatively remove the
Arrangement.spacedBy and apply per-child paddings so only one 16dp gap exists
between the avatar and text; update the code references:
horizontalArrangement/Arrangement.spacedBy(StreamTokens.spacingMd) and the
center content padding (start = StreamTokens.spacing2xs) accordingly.

---

207-213: Remove redundant textStyle override.

The Timestamp composable's default textStyle is ChatTheme.typography.captionDefault.copy(color = ChatTheme.colors.textTertiary, lineHeight = StreamTokens.lineHeightNormal). Since StreamTokens.lineHeightNormal = 20.sp, this explicit override passes identical values and can be removed:

-        Timestamp(
-            date = searchResultItemState.message.createdAt,
-            textStyle = ChatTheme.typography.captionDefault.copy(
-                color = ChatTheme.colors.textTertiary,
-                lineHeight = 20.sp,
-            ),
-        )
+        Timestamp(date = searchResultItemState.message.createdAt)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SearchResultItem.kt`
around lines 207 - 213, The explicit textStyle override on the Timestamp
composable is redundant because Timestamp already defaults to
ChatTheme.typography.captionDefault.copy(color = ChatTheme.colors.textTertiary,
lineHeight = StreamTokens.lineHeightNormal); remove the textStyle parameter from
the Timestamp call (the one using searchResultItemState.message.createdAt) so it
relies on the default style provided by Timestamp/ChatTheme.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/ChannelItem.kt (1)

214-214: Prefer decomposition over an undocumented LongMethod suppression.

DefaultChannelItemCenterContent is now doing multiple responsibilities (title row, preview row, status/mute variants). Splitting into focused helpers would keep it maintainable without suppression.

As per coding guidelines: **/*.kt: Use @OptIn annotations explicitly; avoid suppressions unless documented.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/ChannelItem.kt`
at line 214, The suppression of LongMethod should be removed and
DefaultChannelItemCenterContent refactored into smaller helper composables:
extract the title row rendering into a function like renderChannelTitleRow, the
preview/last-message row into renderChannelPreviewRow, and status/mute and
unread badge logic into renderChannelStatusOrMute; update
DefaultChannelItemCenterContent to compose these helpers, keep parameter lists
minimal and pass only necessary state (channel, lastMessagePreview, isMuted,
isOnline, unreadCount), and add explicit `@OptIn` annotations if any experimental
APIs are used instead of suppressing LongMethod.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/util/MessagePreviewFormatter.kt (1)

63-67: Update public API docs for isDirectMessaging and avoid undocumented suppression.

The new public parameter is missing KDoc, and the new LongMethod suppression should be avoided or explicitly justified.

📝 Proposed KDoc update

     /**
      * Generates a preview text for the given message.
      *
      * `@param` message The message whose data is used to generate the preview text.
      * `@param` currentUser The currently logged in user.
+     * `@param` isDirectMessaging Whether preview formatting should use direct-message rules.
      * `@return` The formatted text representation for the given message.
      */

As per coding guidelines: **/*.kt: Document public APIs with KDoc, including thread expectations and state notes; and avoid suppressions unless documented.

Also applies to: 163-163

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/util/MessagePreviewFormatter.kt`
around lines 63 - 67, Add KDoc for the public function formatMessagePreview and
its new parameter isDirectMessaging: document what the function returns,
expected thread/state assumptions, and explain the boolean’s effect (e.g., how
message preview differs in direct messaging vs channels). Remove the
undocumented `@Suppress`("LongMethod") (or if you must keep it, add a KDoc
justification comment explaining why the method legitimately exceeds length and
why splitting isn't appropriate). Ensure the KDoc appears above the
formatMessagePreview declaration and explicitly describes isDirectMessaging
behavior and any thread/state constraints.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/SearchInput.kt (1)

74-74: Avoid introducing an undocumented LongMethod suppression.

Consider extracting parts of SearchInput (state sync / decoration) into helpers instead of suppressing the rule directly.

As per coding guidelines: **/*.kt: Use @OptIn annotations explicitly; avoid suppressions unless documented.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/SearchInput.kt`
at line 74, Remove the undocumented `@Suppress`("LongMethod") on SearchInput:
instead split the large function by extracting the state synchronization logic
and the TextField decoration into small helpers (e.g., create functions named
syncSearchState(...) and decorateSearchTextField(...) called from SearchInput)
so the body is shorter and the lint rule is satisfied; if any experimental APIs
are required, replace suppressions with explicit `@OptIn`(...) annotations on
SearchInput or the new helper functions and document the reason in a brief KDoc.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SwipeActionStyle.kt (1)

21-36: Add thread/state notes to enum KDoc.

Please include a brief statement about state/thread expectations for this public enum (for example, stateless style marker safe for use from any thread).

As per coding guidelines **/*.kt: Document public APIs with KDoc, including thread expectations and state notes.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SwipeActionStyle.kt`
around lines 21 - 36, The public enum SwipeActionStyle lacks KDoc about
thread/state expectations; update the KDoc for SwipeActionStyle to add a short
thread/state note stating that this enum is a stateless, immutable style marker
and safe to reference from any thread (no synchronization required), and include
that it carries no mutable state and is safe for concurrent use in UI code such
as composables and background threads.

stream-chat-android-ui-common/src/main/kotlin/io/getstream/chat/android/ui/common/state/channels/actions/ConfirmationPopup.kt (1)

19-30: Expand public KDoc with thread/state expectations.

This public API is documented, but it should also state thread expectations and state behavior (for example: immutable value object, safe to pass across threads, fields are resolved UI text).

As per coding guidelines **/*.kt: Document public APIs with KDoc, including thread expectations and state notes.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-ui-common/src/main/kotlin/io/getstream/chat/android/ui/common/state/channels/actions/ConfirmationPopup.kt`
around lines 19 - 30, Update the KDoc for the public data class
ConfirmationPopup to include thread and state expectations: state that this is
an immutable value object (data class) safe to pass across threads, its
properties (title, message, confirmButtonText) are resolved UI text and should
not hold mutable or lifecycle-bound references, and note any expectations about
resolution timing (e.g., already localized/resolved before construction) so
callers know it's safe for background/worker threads and UI usage; reference the
ConfirmationPopup type and its properties when adding these notes.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/DefaultChannelSwipeActions.kt (1)

164-170: firstOrNull { it != null } is equivalent to firstNotNullOfOrNull { it } — but more importantly, for DMs the archive action is always returned.

Since archiveAction and pinAction are never null, the first non-null in the DM list [archiveAction, muteAction, pinAction] is always archiveAction, and in the group list [muteAction, archiveAction, pinAction], it's muteAction if available, otherwise archiveAction. The fallback priority works, but the function can never return null overall (pin is always non-null). Consider simplifying the return type to non-nullable if that's the intent, or use filterNotNull().first().

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/DefaultChannelSwipeActions.kt`
around lines 164 - 170, The current selection logic in
DefaultChannelSwipeActions builds candidates = listOf(...) containing
archiveAction, muteAction, pinAction and then returns candidates.firstOrNull {
it != null }, but since pinAction (and archiveAction/pinAction) are non-null the
function can never return null; update the implementation to reflect that
non-null guarantee: either change the function return type to non-nullable and
return candidates.filterNotNull().first() (or .first { true } after filtering)
or, if null is genuinely possible, adjust the candidates construction so some
entries can be null and use filterNotNull().firstOrNull(); reference the
candidates variable and the archiveAction/muteAction/pinAction symbols when
making the change.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/ChannelOptions.kt (1)

95-95: Document or remove the blanket suppression on buildDefaultChannelActions.

Line 95 adds @Suppress("LongMethod", "LongParameterList") without rationale. Prefer further decomposition (or a scoped justification comment) instead of an undocumented suppression.

As per coding guidelines: **/*.kt: "Use @OptIn annotations explicitly; avoid suppressions unless documented".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/components/channels/ChannelOptions.kt`
at line 95, The suppression on buildDefaultChannelActions is too broad and
undocumented; remove the blanket `@Suppress`("LongMethod", "LongParameterList")
and either refactor buildDefaultChannelActions into smaller helper functions
(e.g., extract action creation into createChannelActionList, buildActionItem,
configureActionHandlers) to reduce method length and parameter count, or if
suppression is unavoidable, replace it with a narrow, documented suppression
scoped to the specific offending expression(s) and add a one-line rationale
comment above it; also ensure any experimental APIs used are annotated with
`@OptIn` rather than suppressed.

stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SwipeRevealCoordinator.kt (1)

26-30: Add thread-confinement notes to public KDoc.

Public methods mutate shared coordinator state, but KDoc doesn’t state thread expectations (e.g., main-thread use) or state guarantees.

As per coding guidelines: **/*.kt: "Document public APIs with KDoc, including thread expectations and state notes".

Also applies to: 34-66

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-compose/src/main/java/io/getstream/chat/android/compose/ui/channels/list/SwipeRevealCoordinator.kt`
around lines 26 - 30, Update the KDoc for the public class
SwipeRevealCoordinator to include thread-confinement and state guarantees:
explicitly state that all public methods that mutate shared coordinator state
must be called from the main/UI thread (or specify the required dispatcher),
describe whether calls are reentrant or synchronized, and note any
atomicity/visibility guarantees clients can rely on; also add the same
thread/state note to each public method in the class so callers see the
requirement at the call site.

stream-chat-android-ui-common/src/main/kotlin/io/getstream/chat/android/ui/common/state/channels/actions/ChannelAction.kt (1)

63-73: Consider safe defaults for destructive actions.

LeaveGroup and DeleteConversation are destructive, but confirmationPopup defaults to null (Line 67, Line 108). That makes accidental immediate execution easy when a caller forgets to pass confirmation metadata.

Also applies to: 104-114

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In
`@stream-chat-android-ui-common/src/main/kotlin/io/getstream/chat/android/ui/common/state/channels/actions/ChannelAction.kt`
around lines 63 - 73, LeaveGroup and DeleteConversation currently have
confirmationPopup defaulting to null making destructive actions prone to
accidental immediate execution; update their constructors (classes LeaveGroup
and DeleteConversation) so confirmationPopup defaults to a safe non-null
ConfirmationPopup (e.g., a standard destructive confirmation with title, message
and confirm/cancel labels) instead of null, and ensure callers can still
override it by providing a custom ConfirmationPopup via the confirmationPopup
parameter declared on the ChannelAction implementations.